Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 587f7504a76eb35f8635f91bef77cd619540ed1dcb0efc28963a52264c86f74d

Tx prefix hash: 9d118571f9e3d9411abc6d8e33f312c5dfae0c337137e1f75ac829fe2d14fd9e
Tx public key: cb4f297b114358fb3aab1bb59b3d5a16b67350d8d3803b0128dab4c72a1a7741
Timestamp: 1730009420 Timestamp [UCT]: 2024-10-27 06:10:20 Age [y:d:h:m:s]: 00:164:11:30:48
Block: 1140509 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 117344 RingCT/type: yes/0
Extra: 01cb4f297b114358fb3aab1bb59b3d5a16b67350d8d3803b0128dab4c72a1a7741021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c69f88bdf9a090183191bbf02e94cb4918ec4bd9a746837b64da0f68259ddd45 0.600000000000 1624308 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": 1140519, "vin": [ { "gen": { "height": 1140509 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c69f88bdf9a090183191bbf02e94cb4918ec4bd9a746837b64da0f68259ddd45" } } ], "extra": [ 1, 203, 79, 41, 123, 17, 67, 88, 251, 58, 171, 27, 181, 155, 61, 90, 22, 182, 115, 80, 216, 211, 128, 59, 1, 40, 218, 180, 199, 42, 26, 119, 65, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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