Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 83aa6ba21cfdcdbbc7bf4eb0c8b5ba7d7f248d2372cacc44efd8033229ca8837

Tx prefix hash: 04a58a59dec8dc2f5a16953bfc9a07375bb2a6dc13a5799089d4f3c22d7c8cf3
Tx public key: 5e5ea9d35440f400bda8bfd900ad88ec6e0065601cf0d274f1c74447180cd7ee
Timestamp: 1701082994 Timestamp [UCT]: 2023-11-27 11:03:14 Age [y:d:h:m:s]: 01:168:04:07:01
Block: 900717 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 381382 RingCT/type: yes/0
Extra: 015e5ea9d35440f400bda8bfd900ad88ec6e0065601cf0d274f1c74447180cd7ee02110000000733af99f4000000000000000000

1 output(s) for total of 0.636136999000 dcy

stealth address amount amount idx
00: 255dcd407bf6f5adbb1c642b9dce885c623dfec24bb48c4e41971482b20ccbd2 0.636136999000 1357232 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": 900727, "vin": [ { "gen": { "height": 900717 } } ], "vout": [ { "amount": 636136999, "target": { "key": "255dcd407bf6f5adbb1c642b9dce885c623dfec24bb48c4e41971482b20ccbd2" } } ], "extra": [ 1, 94, 94, 169, 211, 84, 64, 244, 0, 189, 168, 191, 217, 0, 173, 136, 236, 110, 0, 101, 96, 28, 240, 210, 116, 241, 199, 68, 71, 24, 12, 215, 238, 2, 17, 0, 0, 0, 7, 51, 175, 153, 244, 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