Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e6c0a1ec063aa52fe35e4a471105ed44c4264f9d6d5bd586cc062d14059fb854

Tx prefix hash: 6307abd8b1160693e2a4e1de158e3b3eb957d30d34e1c15cc20ac87e197dae61
Tx public key: ff4e467cfc4122287857a3eee5bbde89c16352505a810f637782d31d87f6617e
Timestamp: 1715218700 Timestamp [UCT]: 2024-05-09 01:38:20 Age [y:d:h:m:s]: 00:335:14:39:17
Block: 1017919 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 239889 RingCT/type: yes/0
Extra: 01ff4e467cfc4122287857a3eee5bbde89c16352505a810f637782d31d87f6617e02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8bba23cd2b6a2d5171ff85763c4804aa4f238f9c1734f4d1270ea46caa7ee480 0.600000000000 1481704 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": 1017929, "vin": [ { "gen": { "height": 1017919 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8bba23cd2b6a2d5171ff85763c4804aa4f238f9c1734f4d1270ea46caa7ee480" } } ], "extra": [ 1, 255, 78, 70, 124, 252, 65, 34, 40, 120, 87, 163, 238, 229, 187, 222, 137, 193, 99, 82, 80, 90, 129, 15, 99, 119, 130, 211, 29, 135, 246, 97, 126, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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