Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9d1bc86f2c3885f7860b24b4ea03205ba4317acd5ef540b111cec7a63ebcd493

Tx prefix hash: 8c82409a058468a047cd39011a50cefc9b4f6b2790ae05d905034a3d7b52ca16
Tx public key: 7c5f0a57f82f8652921fcb882f68ffe6fb5ebf24c540abea28574752f405a652
Timestamp: 1719842906 Timestamp [UCT]: 2024-07-01 14:08:26 Age [y:d:h:m:s]: 00:277:02:26:13
Block: 1056251 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197997 RingCT/type: yes/0
Extra: 017c5f0a57f82f8652921fcb882f68ffe6fb5ebf24c540abea28574752f405a65202110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7fdaab49d52b46bbf7c3dc8741b703d7006bb59f07f9ebd2223cf20c1771d8fb 0.600000000000 1526664 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": 1056261, "vin": [ { "gen": { "height": 1056251 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7fdaab49d52b46bbf7c3dc8741b703d7006bb59f07f9ebd2223cf20c1771d8fb" } } ], "extra": [ 1, 124, 95, 10, 87, 248, 47, 134, 82, 146, 31, 203, 136, 47, 104, 255, 230, 251, 94, 191, 36, 197, 64, 171, 234, 40, 87, 71, 82, 244, 5, 166, 82, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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