Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0184fa89c28433812d54e5f4b66a1970721553bc8aa78733de3c0e9279e4b231

Tx prefix hash: 71088daf7e80f99c38ec307bcf1ed1edbfdcd5c9af24145ae0e3b4edc0d914ef
Tx public key: 336257550bb2dfb46e792b7a977d45bbf2c9283197f17540d4c69e75e89bd7cd
Timestamp: 1711253986 Timestamp [UCT]: 2024-03-24 04:19:46 Age [y:d:h:m:s]: 01:083:18:12:09
Block: 985066 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 320765 RingCT/type: yes/0
Extra: 01336257550bb2dfb46e792b7a977d45bbf2c9283197f17540d4c69e75e89bd7cd0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aa008f7b33495ab66a8c3c23a9a9c7f39dc196d98cdcf6eda42b5572e8300538 0.600000000000 1445273 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": 985076, "vin": [ { "gen": { "height": 985066 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa008f7b33495ab66a8c3c23a9a9c7f39dc196d98cdcf6eda42b5572e8300538" } } ], "extra": [ 1, 51, 98, 87, 85, 11, 178, 223, 180, 110, 121, 43, 122, 151, 125, 69, 187, 242, 201, 40, 49, 151, 241, 117, 64, 212, 198, 158, 117, 232, 155, 215, 205, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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