Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 61ff728f1ec2eae27c7d8d9bfff739dff67a6a598666331f2639388fc3b17a83

Tx prefix hash: 6a09d398d9e9ee48f2120f92cf4b4019ef87c4ffec6c1790e341edd229dfb2c9
Tx public key: fe3173f825931fd2cae0eaaa7d8f487acc0385ed24c0d44ee149fb506fdb6c25
Timestamp: 1741376127 Timestamp [UCT]: 2025-03-07 19:35:27 Age [y:d:h:m:s]: 00:256:03:36:07
Block: 1234320 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180803 RingCT/type: yes/0
Extra: 01fe3173f825931fd2cae0eaaa7d8f487acc0385ed24c0d44ee149fb506fdb6c25021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d7fa0f6fd3ad17af134bf4d4bf3b22d252aff0decf5d18e407785b1d96e7736d 0.600000000000 1721247 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": 1234330, "vin": [ { "gen": { "height": 1234320 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d7fa0f6fd3ad17af134bf4d4bf3b22d252aff0decf5d18e407785b1d96e7736d" } } ], "extra": [ 1, 254, 49, 115, 248, 37, 147, 31, 210, 202, 224, 234, 170, 125, 143, 72, 122, 204, 3, 133, 237, 36, 192, 212, 78, 225, 73, 251, 80, 111, 219, 108, 37, 2, 17, 0, 0, 0, 7, 0, 127, 151, 138, 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