Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 21e1b008630d6731add1d9378392bcaa0cac1879baba65ead248f362998db7ce

Tx prefix hash: f58df8aa7579f5e0c287f846de73d219f433ff9bafdd9d92f7ee66bbb4dcc0dc
Tx public key: 68f8279d8938fc8804a196ba948cf9be519d535866dc81144d4091f2208d77ee
Timestamp: 1577563309 Timestamp [UCT]: 2019-12-28 20:01:49 Age [y:d:h:m:s]: 05:308:05:22:47
Block: 33791 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1367816 RingCT/type: yes/0
Extra: 0168f8279d8938fc8804a196ba948cf9be519d535866dc81144d4091f2208d77ee02110000000c4943cd9f000000000000000000

1 output(s) for total of 474.282659443000 dcy

stealth address amount amount idx
00: 81db9a0e002c23ea31bde8327a49e1b68a379e81581b1ee61c9d2e68eaa89414 474.282659443000 56690 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": 33801, "vin": [ { "gen": { "height": 33791 } } ], "vout": [ { "amount": 474282659443, "target": { "key": "81db9a0e002c23ea31bde8327a49e1b68a379e81581b1ee61c9d2e68eaa89414" } } ], "extra": [ 1, 104, 248, 39, 157, 137, 56, 252, 136, 4, 161, 150, 186, 148, 140, 249, 190, 81, 157, 83, 88, 102, 220, 129, 20, 77, 64, 145, 242, 32, 141, 119, 238, 2, 17, 0, 0, 0, 12, 73, 67, 205, 159, 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