Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f88c9c0b2f5e7d788f0869c0ee4fbaec276185afb21bbec22424699468938cee

Tx prefix hash: 8a5e6df530085e16b87dc025415529a71348bd08a1fa50091163cd8861a7027b
Tx public key: 2c8b1a451365859b4f8faa3e3fe45bf6f23f09858078e56f7558949da1bda632
Timestamp: 1636544196 Timestamp [UCT]: 2021-11-10 11:36:36 Age [y:d:h:m:s]: 03:184:16:01:34
Block: 371367 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 910386 RingCT/type: yes/0
Extra: 012c8b1a451365859b4f8faa3e3fe45bf6f23f09858078e56f7558949da1bda632021100000002f79c6ccf000000000000000000

1 output(s) for total of 36.100013101000 dcy

stealth address amount amount idx
00: fd3fdafe5570d2d95d9c306d89f6fa9603b6373a95287a99beb6bf4eebe1862d 36.100013101000 752587 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": 371377, "vin": [ { "gen": { "height": 371367 } } ], "vout": [ { "amount": 36100013101, "target": { "key": "fd3fdafe5570d2d95d9c306d89f6fa9603b6373a95287a99beb6bf4eebe1862d" } } ], "extra": [ 1, 44, 139, 26, 69, 19, 101, 133, 155, 79, 143, 170, 62, 63, 228, 91, 246, 242, 63, 9, 133, 128, 120, 229, 111, 117, 88, 148, 157, 161, 189, 166, 50, 2, 17, 0, 0, 0, 2, 247, 156, 108, 207, 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