Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 937d7a1e1fe4ddeb294d7c0afbeb908a14d7bc5da81a655366ba52cb8c1c2d96

Tx prefix hash: 413246177be4373d4fbcb38ac8c83324795dfb667b13c5627d9957f690aebada
Tx public key: 5f135b38f5ab80be4f716294d1c233f1ab2c978f1224eeb22c3c6b9b09d47b8e
Timestamp: 1721970097 Timestamp [UCT]: 2024-07-26 05:01:37 Age [y:d:h:m:s]: 00:253:12:59:53
Block: 1073886 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181120 RingCT/type: yes/0
Extra: 015f135b38f5ab80be4f716294d1c233f1ab2c978f1224eeb22c3c6b9b09d47b8e021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dd4d5c6bde03bbeff0aa93696dbf9c610d3262e89c8e613c8f9f00ea6257c1ba 0.600000000000 1546393 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": 1073896, "vin": [ { "gen": { "height": 1073886 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd4d5c6bde03bbeff0aa93696dbf9c610d3262e89c8e613c8f9f00ea6257c1ba" } } ], "extra": [ 1, 95, 19, 91, 56, 245, 171, 128, 190, 79, 113, 98, 148, 209, 194, 51, 241, 171, 44, 151, 143, 18, 36, 238, 178, 44, 60, 107, 155, 9, 212, 123, 142, 2, 17, 0, 0, 0, 9, 233, 20, 221, 21, 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