Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5653f5f22d8de8112b69838b15c047d0a95818f550b30bc1ed988f732dc77896

Tx prefix hash: e4ae614e0b754c5ac0a95d00bfd9239f9a6a467dac3a56d6b0eded7f475eddff
Tx public key: 90314a74be5ac61fe7b3a20395cee349d9b2ff5a380d1e2f8d8460c3309657bd
Timestamp: 1702401305 Timestamp [UCT]: 2023-12-12 17:15:05 Age [y:d:h:m:s]: 01:155:07:34:09
Block: 911673 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 372141 RingCT/type: yes/0
Extra: 0190314a74be5ac61fe7b3a20395cee349d9b2ff5a380d1e2f8d8460c3309657bd02110000000ffaf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 39241268891b9a8a5ef241079c897d16f6c31be15d97e810ec9424034f29e644 0.600000000000 1368887 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": 911683, "vin": [ { "gen": { "height": 911673 } } ], "vout": [ { "amount": 600000000, "target": { "key": "39241268891b9a8a5ef241079c897d16f6c31be15d97e810ec9424034f29e644" } } ], "extra": [ 1, 144, 49, 74, 116, 190, 90, 198, 31, 231, 179, 162, 3, 149, 206, 227, 73, 217, 178, 255, 90, 56, 13, 30, 47, 141, 132, 96, 195, 48, 150, 87, 189, 2, 17, 0, 0, 0, 15, 250, 243, 92, 156, 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