Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 16aba4285f0cd7e0da070ec93772de7119e51729181150ac9001d322b1c88197

Tx prefix hash: b61547bc9481b81918f24ec626bb50d2eb1b3f4d8a90b03926ee77d1e3012206
Tx public key: 3143d713c716cd4eb7544a5bfb0df1182946131e49c61bcab0d5bd8c0f6d6cbf
Timestamp: 1576928360 Timestamp [UCT]: 2019-12-21 11:39:20 Age [y:d:h:m:s]: 04:345:11:13:54
Block: 29314 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1135260 RingCT/type: yes/0
Extra: 013143d713c716cd4eb7544a5bfb0df1182946131e49c61bcab0d5bd8c0f6d6cbf021100000043ad433a0b000000000000000000

1 output(s) for total of 490.762547833000 dcy

stealth address amount amount idx
00: a7dad0500c3f44134108e70c0d1b88066cecb2e22c6da786a25165273648f261 490.762547833000 48146 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 29324, "vin": [ { "gen": { "height": 29314 } } ], "vout": [ { "amount": 490762547833, "target": { "key": "a7dad0500c3f44134108e70c0d1b88066cecb2e22c6da786a25165273648f261" } } ], "extra": [ 1, 49, 67, 215, 19, 199, 22, 205, 78, 183, 84, 74, 91, 251, 13, 241, 24, 41, 70, 19, 30, 73, 198, 27, 202, 176, 213, 189, 140, 15, 109, 108, 191, 2, 17, 0, 0, 0, 67, 173, 67, 58, 11, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8