Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a59945a19deb7a139be8d1358b0f75437ca2a521c881ad8ca3bc89e045899ff

Tx prefix hash: 659d971dd1f59e5fe796d1ddcce05b986231440bdaec2e47b59a2cd616d69e6f
Tx public key: e6dd36c65e963351dc8f43814ea9a94aa1a39cd8910016f0bd454e4ee6cfaf1e
Timestamp: 1709370479 Timestamp [UCT]: 2024-03-02 09:07:59 Age [y:d:h:m:s]: 01:038:02:41:33
Block: 969434 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288254 RingCT/type: yes/0
Extra: 01e6dd36c65e963351dc8f43814ea9a94aa1a39cd8910016f0bd454e4ee6cfaf1e0211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600010000000 dcy

stealth address amount amount idx
00: e6c29ec4302e9b6a911c035a7f8b2d7ba25a7317080e70ceb2779b9f4388c10e 0.600010000000 1429263 of 0

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": 969444, "vin": [ { "gen": { "height": 969434 } } ], "vout": [ { "amount": 600010000, "target": { "key": "e6c29ec4302e9b6a911c035a7f8b2d7ba25a7317080e70ceb2779b9f4388c10e" } } ], "extra": [ 1, 230, 221, 54, 198, 94, 150, 51, 81, 220, 143, 67, 129, 78, 169, 169, 74, 161, 163, 156, 216, 145, 0, 22, 240, 189, 69, 78, 78, 230, 207, 175, 30, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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