Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7cb975a845a521602de9177bc7290e47409d98251d121cd03eab15432a595ab4

Tx prefix hash: f7723b48aa4be9525828c6abbd6a7a0a5f0a98f5b01f33c508bb21f554d80087
Tx public key: eb33ad4477c3c86088cc54b4d6905f02f3eaf24caaae3915dc8040d840700690
Timestamp: 1730912731 Timestamp [UCT]: 2024-11-06 17:05:31 Age [y:d:h:m:s]: 00:000:19:29:28
Block: 1147938 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 586 RingCT/type: yes/0
Extra: 01eb33ad4477c3c86088cc54b4d6905f02f3eaf24caaae3915dc8040d840700690021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3670078d2891a4cf1a6dcbe8d84f4c38129ad9d1e499f90d1632c9f616504cbf 0.600000000000 1632655 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": 1147948, "vin": [ { "gen": { "height": 1147938 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3670078d2891a4cf1a6dcbe8d84f4c38129ad9d1e499f90d1632c9f616504cbf" } } ], "extra": [ 1, 235, 51, 173, 68, 119, 195, 200, 96, 136, 204, 84, 180, 214, 144, 95, 2, 243, 234, 242, 76, 170, 174, 57, 21, 220, 128, 64, 216, 64, 112, 6, 144, 2, 17, 0, 0, 0, 2, 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