Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3e8b1ff6a30cd578c2467883b4ca7675bd5ac9eec3b888519c38f46bf6472c5

Tx prefix hash: 2e5c8071445cc00bc3e4e50f3c0eb19ee6a46baa4d499c18da0a380e696e8171
Tx public key: 85f73f4ddbc9b9c411287bbea04f3dc84186675e392f33a0253cae8ace4fb76d
Timestamp: 1737223770 Timestamp [UCT]: 2025-01-18 18:09:30 Age [y:d:h:m:s]: 00:151:11:05:20
Block: 1200170 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107962 RingCT/type: yes/0
Extra: 0185f73f4ddbc9b9c411287bbea04f3dc84186675e392f33a0253cae8ace4fb76d0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a061e9d985e69d8c3db513cd2dd8b71147fc8b0341f90ece9923e83bf9848713 0.600000000000 1686811 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": 1200180, "vin": [ { "gen": { "height": 1200170 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a061e9d985e69d8c3db513cd2dd8b71147fc8b0341f90ece9923e83bf9848713" } } ], "extra": [ 1, 133, 247, 63, 77, 219, 201, 185, 196, 17, 40, 123, 190, 160, 79, 61, 200, 65, 134, 103, 94, 57, 47, 51, 160, 37, 60, 174, 138, 206, 79, 183, 109, 2, 17, 0, 0, 0, 4, 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