Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7aa3a9799f41a108a1fbc7e705589f0cbe3d3ce2447598856a15a4db4afdfe6

Tx prefix hash: d55bad9ea5462c6efdd044b2884310fa66efdacd3c4072afce57c08a28c6b4bd
Tx public key: 6842e2de6e5a59ffdff1cf0f03d15f58b94c1991496af3be1d4e3be287b11be1
Timestamp: 1751412754 Timestamp [UCT]: 2025-07-01 23:32:34 Age [y:d:h:m:s]: 00:142:04:32:28
Block: 1316855 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99837 RingCT/type: yes/0
Extra: 016842e2de6e5a59ffdff1cf0f03d15f58b94c1991496af3be1d4e3be287b11be102110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 98785f6d8432a9d6c6183781b2eb41500a5b3093af8ebf8e51ba58df696c611e 0.600000000000 1804518 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": 1316865, "vin": [ { "gen": { "height": 1316855 } } ], "vout": [ { "amount": 600000000, "target": { "key": "98785f6d8432a9d6c6183781b2eb41500a5b3093af8ebf8e51ba58df696c611e" } } ], "extra": [ 1, 104, 66, 226, 222, 110, 90, 89, 255, 223, 241, 207, 15, 3, 209, 95, 88, 185, 76, 25, 145, 73, 106, 243, 190, 29, 78, 59, 226, 135, 177, 27, 225, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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