Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e72d82c96f81e32f074f97c2ae62b8187b6fab019913717e64a75ffe8204eb92

Tx prefix hash: 9b0dac513ae238cc3a82a357ad9392c92b3a930f7f0bffc4f18fa4013d63725a
Tx public key: 6f4c9bb1348df89a63309785dc4ef98a32f401e7617e619bd61aba006bb562e7
Timestamp: 1713261858 Timestamp [UCT]: 2024-04-16 10:04:18 Age [y:d:h:m:s]: 00:317:17:28:36
Block: 1001679 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 227133 RingCT/type: yes/0
Extra: 016f4c9bb1348df89a63309785dc4ef98a32f401e7617e619bd61aba006bb562e702110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f98e90e3ac6d32b7cf295aa93f953663e95c435ae7d533f621aff6f42dac2504 0.600000000000 1462187 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": 1001689, "vin": [ { "gen": { "height": 1001679 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f98e90e3ac6d32b7cf295aa93f953663e95c435ae7d533f621aff6f42dac2504" } } ], "extra": [ 1, 111, 76, 155, 177, 52, 141, 248, 154, 99, 48, 151, 133, 220, 78, 249, 138, 50, 244, 1, 231, 97, 126, 97, 155, 214, 26, 186, 0, 107, 181, 98, 231, 2, 17, 0, 0, 0, 1, 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