Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b31fcfea97d1a034e6ed31446dcad5c6a1e0b687e11c27386dd1eecd1426850d

Tx prefix hash: 3719436f03fb1cf121078b51e3057e240a08da6ee3dd04447519d4a4abf04337
Tx public key: 3a266fd3fd921028d55a81c13197f01f65e1e895367d0d70d3333e49d38ee38a
Timestamp: 1713446219 Timestamp [UCT]: 2024-04-18 13:16:59 Age [y:d:h:m:s]: 00:351:16:46:16
Block: 1003204 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 251441 RingCT/type: yes/0
Extra: 013a266fd3fd921028d55a81c13197f01f65e1e895367d0d70d3333e49d38ee38a02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4ceb18ae11c8ea1e5130ed1341289fe08b1ddf4716a5f3d3aa119e959d68b14f 0.600000000000 1463734 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": 1003214, "vin": [ { "gen": { "height": 1003204 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ceb18ae11c8ea1e5130ed1341289fe08b1ddf4716a5f3d3aa119e959d68b14f" } } ], "extra": [ 1, 58, 38, 111, 211, 253, 146, 16, 40, 213, 90, 129, 193, 49, 151, 240, 31, 101, 225, 232, 149, 54, 125, 13, 112, 211, 51, 62, 73, 211, 142, 227, 138, 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