Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6bff831a98e29fbbcbb77f1d44ad42dc51163dcf5cf343507b97f93aa8c94979

Tx prefix hash: 5e40b6b6054d204fcaea793d42ca993bca7acfc18bb25d69d2d7bcea9a0eac81
Tx public key: 18877ce901b226b7f9db4a76e14ad8891fa0bd60df7bdce8ec2b428d04251b61
Timestamp: 1740654904 Timestamp [UCT]: 2025-02-27 11:15:04 Age [y:d:h:m:s]: 00:267:12:07:53
Block: 1228334 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 188939 RingCT/type: yes/0
Extra: 0118877ce901b226b7f9db4a76e14ad8891fa0bd60df7bdce8ec2b428d04251b610211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 803d6ea85c5784fbdcf7f519768bbc772620593a853d44b77d231be7dc776fe8 0.600000000000 1715211 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": 1228344, "vin": [ { "gen": { "height": 1228334 } } ], "vout": [ { "amount": 600000000, "target": { "key": "803d6ea85c5784fbdcf7f519768bbc772620593a853d44b77d231be7dc776fe8" } } ], "extra": [ 1, 24, 135, 124, 233, 1, 178, 38, 183, 249, 219, 74, 118, 225, 74, 216, 137, 31, 160, 189, 96, 223, 123, 220, 232, 236, 43, 66, 141, 4, 37, 27, 97, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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