Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be00915cb090a6ce411c37fa6f23523b0c75410de56997bd9ca67411da094ae3

Tx prefix hash: 0a1315d8a807aec5b50605ae7bf227f69325feb5bac4cf0238bf1b9223e0ec95
Tx public key: 61e604c19ac8d1154b5d1e3969c01a0a76e6dc2453335d40660fe3ed5602b9c5
Timestamp: 1703120657 Timestamp [UCT]: 2023-12-21 01:04:17 Age [y:d:h:m:s]: 01:119:16:51:25
Block: 917634 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 346670 RingCT/type: yes/0
Extra: 0161e604c19ac8d1154b5d1e3969c01a0a76e6dc2453335d40660fe3ed5602b9c5021100000002bfa22221000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 50fa12d7924914855c14d01b6f8a7f60ef4cbb008ed881a794892487ce9b5f69 0.600000000000 1375216 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": 917644, "vin": [ { "gen": { "height": 917634 } } ], "vout": [ { "amount": 600000000, "target": { "key": "50fa12d7924914855c14d01b6f8a7f60ef4cbb008ed881a794892487ce9b5f69" } } ], "extra": [ 1, 97, 230, 4, 193, 154, 200, 209, 21, 75, 93, 30, 57, 105, 192, 26, 10, 118, 230, 220, 36, 83, 51, 93, 64, 102, 15, 227, 237, 86, 2, 185, 197, 2, 17, 0, 0, 0, 2, 191, 162, 34, 33, 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