Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f005a1843bb4b41ac83ac82c804ca3da4ae75dcc917bf313cee47e136827de7c

Tx prefix hash: 326789ef30cc30157e270cf8d62e6db2fa01b8286fa0ebf5ba48e5a5df233e88
Tx public key: 2c699893b44652e00d975e04043a08f3f67eb4f31727854c720324d0f9e3dc28
Timestamp: 1719934703 Timestamp [UCT]: 2024-07-02 15:38:23 Age [y:d:h:m:s]: 01:129:04:31:06
Block: 1057025 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 350847 RingCT/type: yes/0
Extra: 012c699893b44652e00d975e04043a08f3f67eb4f31727854c720324d0f9e3dc280211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c5e6483faf98b4b72c879be72a069100f060762e7b3b5fa8457c1516472e60a9 0.600000000000 1527454 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": 1057035, "vin": [ { "gen": { "height": 1057025 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c5e6483faf98b4b72c879be72a069100f060762e7b3b5fa8457c1516472e60a9" } } ], "extra": [ 1, 44, 105, 152, 147, 180, 70, 82, 224, 13, 151, 94, 4, 4, 58, 8, 243, 246, 126, 180, 243, 23, 39, 133, 76, 114, 3, 36, 208, 249, 227, 220, 40, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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