Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a55b28839f0b2db0fd360e701b6ad09a91036304895a8bbfb6469cba8385718f

Tx prefix hash: 2ca5e9553f00813d2c8b6055d61f8c06ec20f98b956091a3fe348191928fb81e
Tx public key: eb59936b7f415a783e753c1dfbcca7a94dd03e479f6d2a0870af0af5496a4648
Timestamp: 1648402633 Timestamp [UCT]: 2022-03-27 17:37:13 Age [y:d:h:m:s]: 03:219:04:48:17
Block: 467635 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 934586 RingCT/type: yes/0
Extra: 01eb59936b7f415a783e753c1dfbcca7a94dd03e479f6d2a0870af0af5496a46480211000000182e6b1fd5000000000000000000

1 output(s) for total of 17.319341411000 dcy

stealth address amount amount idx
00: cd97649a94f767ee360513e2430411bafa889149db6e6154fccd582cd6d1e352 17.319341411000 886180 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": 467645, "vin": [ { "gen": { "height": 467635 } } ], "vout": [ { "amount": 17319341411, "target": { "key": "cd97649a94f767ee360513e2430411bafa889149db6e6154fccd582cd6d1e352" } } ], "extra": [ 1, 235, 89, 147, 107, 127, 65, 90, 120, 62, 117, 60, 29, 251, 204, 167, 169, 77, 208, 62, 71, 159, 109, 42, 8, 112, 175, 10, 245, 73, 106, 70, 72, 2, 17, 0, 0, 0, 24, 46, 107, 31, 213, 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