Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f6891f85f70bab052553c5173a6de017a54bbcca003b5b7a5c97a9723bdd7e0

Tx prefix hash: 510522a7b84450d9121fd557645f5053ecee4610924a7f1a8f15c26bad656579
Tx public key: 1ce5024ba7915d9d6effef6475be9f9736ca6f630b5ab75c66dc5067869b815d
Timestamp: 1631603368 Timestamp [UCT]: 2021-09-14 07:09:28 Age [y:d:h:m:s]: 04:047:19:49:45
Block: 333475 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1068172 RingCT/type: yes/0
Extra: 011ce5024ba7915d9d6effef6475be9f9736ca6f630b5ab75c66dc5067869b815d02110000001f8d0de867000000000000000000

1 output(s) for total of 48.201364703000 dcy

stealth address amount amount idx
00: 09dbb57ebc28470bf2841d71596aa13e626e83de76b4061d1767e8381c6fd2c3 48.201364703000 688128 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": 333485, "vin": [ { "gen": { "height": 333475 } } ], "vout": [ { "amount": 48201364703, "target": { "key": "09dbb57ebc28470bf2841d71596aa13e626e83de76b4061d1767e8381c6fd2c3" } } ], "extra": [ 1, 28, 229, 2, 75, 167, 145, 93, 157, 110, 255, 239, 100, 117, 190, 159, 151, 54, 202, 111, 99, 11, 90, 183, 92, 102, 220, 80, 103, 134, 155, 129, 93, 2, 17, 0, 0, 0, 31, 141, 13, 232, 103, 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