Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2cf91c7413dd072cbc9ec934791ba087e35c6c9d1af583cff6ca17e46468841

Tx prefix hash: 1bfb4ae3d6c35998ccb73ff37a1bcff4d997072dd163f4fade17b81b458870f3
Tx public key: dfbcf6e70eeb55acc57c7acc6853bf1340c18d327a64b6177d847a8991cbc64f
Timestamp: 1702285121 Timestamp [UCT]: 2023-12-11 08:58:41 Age [y:d:h:m:s]: 00:348:21:19:50
Block: 910691 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 249803 RingCT/type: yes/0
Extra: 01dfbcf6e70eeb55acc57c7acc6853bf1340c18d327a64b6177d847a8991cbc64f02110000000233af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a82e0706d13dc33b3fed902379e19a4ca62d62c1f2533bc26cc613ad6539afc5 0.600000000000 1367856 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": 910701, "vin": [ { "gen": { "height": 910691 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a82e0706d13dc33b3fed902379e19a4ca62d62c1f2533bc26cc613ad6539afc5" } } ], "extra": [ 1, 223, 188, 246, 231, 14, 235, 85, 172, 197, 124, 122, 204, 104, 83, 191, 19, 64, 193, 141, 50, 122, 100, 182, 23, 125, 132, 122, 137, 145, 203, 198, 79, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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