Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: faae7502f105ac5f80d5e3ae0e3b45c46faf6e087f989e53644050383939202d

Tx prefix hash: e2187ec089905e1296066b4f84853aa91ac2e62a892c3d298c65e4d07781dcd2
Tx public key: 6daa9d8632cfeb6d48cb53c2bbaabad9361a0c2149e62491df6b9c3c88f438aa
Timestamp: 1745011214 Timestamp [UCT]: 2025-04-18 21:20:14 Age [y:d:h:m:s]: 00:019:16:32:48
Block: 1264413 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 14074 RingCT/type: yes/0
Extra: 016daa9d8632cfeb6d48cb53c2bbaabad9361a0c2149e62491df6b9c3c88f438aa0211000000016c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 738ce99009ca2b802ff7c2934219f6c0333e1d2ff1282256ed00b74b5ad26d8e 0.600000000000 1751610 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": 1264423, "vin": [ { "gen": { "height": 1264413 } } ], "vout": [ { "amount": 600000000, "target": { "key": "738ce99009ca2b802ff7c2934219f6c0333e1d2ff1282256ed00b74b5ad26d8e" } } ], "extra": [ 1, 109, 170, 157, 134, 50, 207, 235, 109, 72, 203, 83, 194, 187, 170, 186, 217, 54, 26, 12, 33, 73, 230, 36, 145, 223, 107, 156, 60, 136, 244, 56, 170, 2, 17, 0, 0, 0, 1, 108, 152, 170, 61, 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