Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f1d94e6a56b057e4c61115eab41949a62989d404026dc01eb9874e6ad065f79

Tx prefix hash: bc1150d3ea7ce43463f8c9da57d56758fcff63c566ec9d8df88d50a7009e3daa
Tx public key: a9d0b8bfa42ebc56ccc27c5947596696d1828f20eb924df523f70bc751d863d4
Timestamp: 1635586556 Timestamp [UCT]: 2021-10-30 09:35:56 Age [y:d:h:m:s]: 03:161:02:27:08
Block: 363554 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 893407 RingCT/type: yes/0
Extra: 01a9d0b8bfa42ebc56ccc27c5947596696d1828f20eb924df523f70bc751d863d4021100000008328bb496000000000000000000

1 output(s) for total of 38.317316238000 dcy

stealth address amount amount idx
00: 300ab32bb748382f5749f7879c021e064b77f059873c22357401ec638ccf0552 38.317316238000 738864 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": 363564, "vin": [ { "gen": { "height": 363554 } } ], "vout": [ { "amount": 38317316238, "target": { "key": "300ab32bb748382f5749f7879c021e064b77f059873c22357401ec638ccf0552" } } ], "extra": [ 1, 169, 208, 184, 191, 164, 46, 188, 86, 204, 194, 124, 89, 71, 89, 102, 150, 209, 130, 143, 32, 235, 146, 77, 245, 35, 247, 11, 199, 81, 216, 99, 212, 2, 17, 0, 0, 0, 8, 50, 139, 180, 150, 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