Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 23a48038166f0f020308f512a37eeac181f3dad572728e43c5362d1d2c2853d7

Tx prefix hash: ef06f0e0c63276ee57d64a36fdd1a99d9fa809298de4dc498451a6fe610ce3c5
Tx public key: b374c7b9e47a048010df4a117011d2ed76f037858cb6e9af3e9a42f31f2f5bad
Timestamp: 1674133575 Timestamp [UCT]: 2023-01-19 13:06:15 Age [y:d:h:m:s]: 02:038:02:29:16
Block: 678164 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 548862 RingCT/type: yes/0
Extra: 01b374c7b9e47a048010df4a117011d2ed76f037858cb6e9af3e9a42f31f2f5bad02110000000152542ceb000000000000000000

1 output(s) for total of 3.475050290000 dcy

stealth address amount amount idx
00: e24814c173e1ca1f7d258080b8e80c9bde03a99d83ea5b897773e7ef2d1fcd1d 3.475050290000 1120001 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": 678174, "vin": [ { "gen": { "height": 678164 } } ], "vout": [ { "amount": 3475050290, "target": { "key": "e24814c173e1ca1f7d258080b8e80c9bde03a99d83ea5b897773e7ef2d1fcd1d" } } ], "extra": [ 1, 179, 116, 199, 185, 228, 122, 4, 128, 16, 223, 74, 17, 112, 17, 210, 237, 118, 240, 55, 133, 140, 182, 233, 175, 62, 154, 66, 243, 31, 47, 91, 173, 2, 17, 0, 0, 0, 1, 82, 84, 44, 235, 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