Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b1929edd9917da41d4f50816dcb43f51f663022dd2a894f14c9352c91a7aa5f0

Tx prefix hash: e52591ca866b3f361b5b01957f5add8daf825301f9f97ffd99d5cff3ff8590fa
Tx public key: 5bc57c4ce482d2a7c0ca76d43f9dc7efb88d32f3ed7bc9362b0206179567e9ac
Timestamp: 1711178511 Timestamp [UCT]: 2024-03-23 07:21:51 Age [y:d:h:m:s]: 01:200:05:29:06
Block: 984446 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 401724 RingCT/type: yes/0
Extra: 015bc57c4ce482d2a7c0ca76d43f9dc7efb88d32f3ed7bc9362b0206179567e9ac0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 119cfaddf868e4771bef5f189f178b251396008bf8c67334182184a6a7229d2b 0.600000000000 1444617 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": 984456, "vin": [ { "gen": { "height": 984446 } } ], "vout": [ { "amount": 600000000, "target": { "key": "119cfaddf868e4771bef5f189f178b251396008bf8c67334182184a6a7229d2b" } } ], "extra": [ 1, 91, 197, 124, 76, 228, 130, 210, 167, 192, 202, 118, 212, 63, 157, 199, 239, 184, 141, 50, 243, 237, 123, 201, 54, 43, 2, 6, 23, 149, 103, 233, 172, 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