Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d58ccfffd75bc0daac3b59027bd828562cb64fe76cc710a7188e7a17f599e7d0

Tx prefix hash: 80ab6dafbc683f6901d747b5d075631918fa2d2b76f52d6ad1c529bda7f9c006
Tx public key: 4e166d1e53f1c934b0c64e6f6c813904be2f558bda7d00ca6a41081dde136f30
Timestamp: 1736779498 Timestamp [UCT]: 2025-01-13 14:44:58 Age [y:d:h:m:s]: 00:063:20:30:18
Block: 1196528 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 45421 RingCT/type: yes/0
Extra: 014e166d1e53f1c934b0c64e6f6c813904be2f558bda7d00ca6a41081dde136f300211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a2272b4b367471488ffc84ed90ea73528815a49e5771cebf44dc0005f201d38 0.600000000000 1683127 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": 1196538, "vin": [ { "gen": { "height": 1196528 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a2272b4b367471488ffc84ed90ea73528815a49e5771cebf44dc0005f201d38" } } ], "extra": [ 1, 78, 22, 109, 30, 83, 241, 201, 52, 176, 198, 78, 111, 108, 129, 57, 4, 190, 47, 85, 139, 218, 125, 0, 202, 106, 65, 8, 29, 222, 19, 111, 48, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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