Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 481a6bf2d197d332ff5793689a92c74c507b583a56f5878c354b71ff99d7b5e6

Tx prefix hash: 226332c44c6f67f795913b736ae7fea3b4da48bc8167bf90db743b1aa0f2f017
Tx public key: 0374a4e66cbe1ef653d8362962b9d791357bbea6e5b1bf7cb70bbe3aa5bfaa47
Timestamp: 1730443356 Timestamp [UCT]: 2024-11-01 06:42:36 Age [y:d:h:m:s]: 00:081:21:32:08
Block: 1144055 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 58553 RingCT/type: yes/0
Extra: 010374a4e66cbe1ef653d8362962b9d791357bbea6e5b1bf7cb70bbe3aa5bfaa47021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 639ffb411edbb22312bc4adfeea825e9e605f8c371feb345e64dd09d5592b85c 0.600000000000 1628134 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": 1144065, "vin": [ { "gen": { "height": 1144055 } } ], "vout": [ { "amount": 600000000, "target": { "key": "639ffb411edbb22312bc4adfeea825e9e605f8c371feb345e64dd09d5592b85c" } } ], "extra": [ 1, 3, 116, 164, 230, 108, 190, 30, 246, 83, 216, 54, 41, 98, 185, 215, 145, 53, 123, 190, 166, 229, 177, 191, 124, 183, 11, 190, 58, 165, 191, 170, 71, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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