Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d4c4a61fc24808c6b1cb07a385614dbf462e2d9b477888f460e42ccc585627bf

Tx prefix hash: 8511813dcdf31ad6d5a7cca0a90f16d9a07b155e859a63febba52842b5492e59
Tx public key: 401e56fc8c65d7c6d7e5fbdc17002a4b60b602e3b014356ccbf68ba1b811b694
Timestamp: 1729073532 Timestamp [UCT]: 2024-10-16 10:12:12 Age [y:d:h:m:s]: 00:211:09:28:06
Block: 1132796 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 150868 RingCT/type: yes/0
Extra: 01401e56fc8c65d7c6d7e5fbdc17002a4b60b602e3b014356ccbf68ba1b811b694021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bacbcf0734ece59aa328c31e6bf7994c9004221be1618b898513c029e9a48eab 0.600000000000 1615797 of 15

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": 1132806, "vin": [ { "gen": { "height": 1132796 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bacbcf0734ece59aa328c31e6bf7994c9004221be1618b898513c029e9a48eab" } } ], "extra": [ 1, 64, 30, 86, 252, 140, 101, 215, 198, 215, 229, 251, 220, 23, 0, 42, 75, 96, 182, 2, 227, 176, 20, 53, 108, 203, 246, 139, 161, 184, 17, 182, 148, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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