Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d1f95f8d682d0c48b810f634e365976bff15cbd50efe57f0e0d9d194610ee08d

Tx prefix hash: c5d809a12d1a0d8ce053b7d433bcfb487ef03a978952cadbb482f91bc4a8d1b1
Tx public key: 8bae438ada661cdfb6df13266d8c9ebbf17e0e52fbeb2414cc2f4b4c905ab176
Timestamp: 1713046120 Timestamp [UCT]: 2024-04-13 22:08:40 Age [y:d:h:m:s]: 01:235:13:49:35
Block: 999886 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 427089 RingCT/type: yes/0
Extra: 018bae438ada661cdfb6df13266d8c9ebbf17e0e52fbeb2414cc2f4b4c905ab1760211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 42fb24ddf48db3d76ab89cf87ba3be1f6fee835525a3c7b4102288226ac2ef43 0.600000000000 1460374 of 15

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": 999896, "vin": [ { "gen": { "height": 999886 } } ], "vout": [ { "amount": 600000000, "target": { "key": "42fb24ddf48db3d76ab89cf87ba3be1f6fee835525a3c7b4102288226ac2ef43" } } ], "extra": [ 1, 139, 174, 67, 138, 218, 102, 28, 223, 182, 223, 19, 38, 109, 140, 158, 187, 241, 126, 14, 82, 251, 235, 36, 20, 204, 47, 75, 76, 144, 90, 177, 118, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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