Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad5760d6ed4ed05b75d4b226d33b908165225ab0b62515a9efcc0630f8a0f842

Tx prefix hash: 2ff6f7faf61c94e2a54580c886a41946322e292b166d792515d2e894a7cc062c
Tx public key: 72680ca9deb0749c44e99b78d8c3c6e0bdf4892203f6f81306be22670a44589e
Timestamp: 1704692223 Timestamp [UCT]: 2024-01-08 05:37:03 Age [y:d:h:m:s]: 01:067:17:41:17
Block: 930622 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 309550 RingCT/type: yes/0
Extra: 0172680ca9deb0749c44e99b78d8c3c6e0bdf4892203f6f81306be22670a44589e0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 25cf2d82a859f8284712fe4f01cf37dcfd7c2acc0b948d659ba67fad62382a8c 0.600000000000 1388506 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": 930632, "vin": [ { "gen": { "height": 930622 } } ], "vout": [ { "amount": 600000000, "target": { "key": "25cf2d82a859f8284712fe4f01cf37dcfd7c2acc0b948d659ba67fad62382a8c" } } ], "extra": [ 1, 114, 104, 12, 169, 222, 176, 116, 156, 68, 233, 155, 120, 216, 195, 198, 224, 189, 244, 137, 34, 3, 246, 248, 19, 6, 190, 34, 103, 10, 68, 88, 158, 2, 17, 0, 0, 0, 4, 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