Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8692f5f055340b9ca108b8051773629c5dd7bc125a644b5955a9f36e259753a5

Tx prefix hash: 5d369996f8d108b6bde614bbfeebb38b697a96d1818070d3450b4056223fc8a1
Tx public key: 60f64400ccc021f6fccee8d4f7f2f8a05f3a1ea640ffee0e24df771755d521b8
Timestamp: 1579338305 Timestamp [UCT]: 2020-01-18 09:05:05 Age [y:d:h:m:s]: 05:298:09:30:40
Block: 48076 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1361183 RingCT/type: yes/0
Extra: 0160f64400ccc021f6fccee8d4f7f2f8a05f3a1ea640ffee0e24df771755d521b8021100000002dcee4b4d000000000000000000

1 output(s) for total of 425.309506843000 dcy

stealth address amount amount idx
00: 9deee89aaf7e7e3720374e0e4c4a77941cbe85bf6a693230ca935fce1b5259e5 425.309506843000 88946 of 0

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": 48086, "vin": [ { "gen": { "height": 48076 } } ], "vout": [ { "amount": 425309506843, "target": { "key": "9deee89aaf7e7e3720374e0e4c4a77941cbe85bf6a693230ca935fce1b5259e5" } } ], "extra": [ 1, 96, 246, 68, 0, 204, 192, 33, 246, 252, 206, 232, 212, 247, 242, 248, 160, 95, 58, 30, 166, 64, 255, 238, 14, 36, 223, 119, 23, 85, 213, 33, 184, 2, 17, 0, 0, 0, 2, 220, 238, 75, 77, 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