Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 972b1a1a593fbe6d862331bc7ea5726ef16f0bc4e1d22abde48053bb5c803c5b

Tx prefix hash: f67fb325144e863fdf51859db4984826ad941eb4b838622abf03c1b7db0c2953
Tx public key: f2b9791e32d7419f6e7c6b5e79a0b965c2dd8d7a3ab5a77df0cf4054e27913e4
Timestamp: 1715406242 Timestamp [UCT]: 2024-05-11 05:44:02 Age [y:d:h:m:s]: 01:004:22:52:18
Block: 1019499 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 264430 RingCT/type: yes/0
Extra: 01f2b9791e32d7419f6e7c6b5e79a0b965c2dd8d7a3ab5a77df0cf4054e27913e4021100000003679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 966fd299eabf2be10243ec46cad7614dc18782aa1e67b9975190d1800022bcf0 0.600000000000 1483480 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": 1019509, "vin": [ { "gen": { "height": 1019499 } } ], "vout": [ { "amount": 600000000, "target": { "key": "966fd299eabf2be10243ec46cad7614dc18782aa1e67b9975190d1800022bcf0" } } ], "extra": [ 1, 242, 185, 121, 30, 50, 215, 65, 159, 110, 124, 107, 94, 121, 160, 185, 101, 194, 221, 141, 122, 58, 181, 167, 125, 240, 207, 64, 84, 226, 121, 19, 228, 2, 17, 0, 0, 0, 3, 103, 154, 138, 129, 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