Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 100547a92514c6d5d6439fca293410ca569bebbbde1b5aef32a44ab206732683

Tx prefix hash: ce72018ebcdec1f05166b5bc9b4c0fb7e404293a4e269359de94be52f772fb53
Tx public key: 6a802cb542f8fe8c16773576285227b2d74569c845f270c5d3f2aee10f7a1a6e
Timestamp: 1673906095 Timestamp [UCT]: 2023-01-16 21:54:55 Age [y:d:h:m:s]: 02:296:02:23:36
Block: 676274 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 731013 RingCT/type: yes/0
Extra: 016a802cb542f8fe8c16773576285227b2d74569c845f270c5d3f2aee10f7a1a6e0211000000028b7b6602000000000000000000

1 output(s) for total of 3.525522181000 dcy

stealth address amount amount idx
00: 0ab7dee40fcaa3e20fe1bb16fec4786559fcd18a943abe4ced8c903022e20aed 3.525522181000 1117983 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": 676284, "vin": [ { "gen": { "height": 676274 } } ], "vout": [ { "amount": 3525522181, "target": { "key": "0ab7dee40fcaa3e20fe1bb16fec4786559fcd18a943abe4ced8c903022e20aed" } } ], "extra": [ 1, 106, 128, 44, 181, 66, 248, 254, 140, 22, 119, 53, 118, 40, 82, 39, 178, 215, 69, 105, 200, 69, 242, 112, 197, 211, 242, 174, 225, 15, 122, 26, 110, 2, 17, 0, 0, 0, 2, 139, 123, 102, 2, 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