Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e7b9666400cd1af4f62c5293cad58c1c3840f5c848e4e1d220415623a4f55497

Tx prefix hash: 25c5f60602527e0b58a8e86ea85c0ac10fa5f3a6e66ddf4cbc5e69606df1408d
Tx public key: 85b769e6c45d8320f09c5b2cce3d3dd84630ab288549e723f32b57fe7833cb21
Timestamp: 1736046489 Timestamp [UCT]: 2025-01-05 03:08:09 Age [y:d:h:m:s]: 00:351:03:10:32
Block: 1190456 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 248500 RingCT/type: yes/0
Extra: 0185b769e6c45d8320f09c5b2cce3d3dd84630ab288549e723f32b57fe7833cb210211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: be56ce1aff3a4e7a55754bce8e0a368c2bbf60ebfc5a11e9cb619af1a92b056a 0.600000000000 1676973 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": 1190466, "vin": [ { "gen": { "height": 1190456 } } ], "vout": [ { "amount": 600000000, "target": { "key": "be56ce1aff3a4e7a55754bce8e0a368c2bbf60ebfc5a11e9cb619af1a92b056a" } } ], "extra": [ 1, 133, 183, 105, 230, 196, 93, 131, 32, 240, 156, 91, 44, 206, 61, 61, 216, 70, 48, 171, 40, 133, 73, 231, 35, 243, 43, 87, 254, 120, 51, 203, 33, 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