Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 000ea0e6266f0a9b56590799aa302693cb2907c44d876c16a8762805d4f8a6a1

Tx prefix hash: b78eb87375f37d17d6c8d1e91673f8368c2dde834787a1c81d577d674365dfe2
Tx public key: d45f713a884411bb48cdec69fb2eeee8f2bcf8e81c9bce0d2a073071442fedde
Timestamp: 1729752972 Timestamp [UCT]: 2024-10-24 06:56:12 Age [y:d:h:m:s]: 01:027:20:13:41
Block: 1138385 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 278277 RingCT/type: yes/0
Extra: 01d45f713a884411bb48cdec69fb2eeee8f2bcf8e81c9bce0d2a073071442fedde021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2b8137a753fa340f154dae4cb6131b704007b8eaa69eb442fb3acf98fd05393f 0.600000000000 1622038 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": 1138395, "vin": [ { "gen": { "height": 1138385 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2b8137a753fa340f154dae4cb6131b704007b8eaa69eb442fb3acf98fd05393f" } } ], "extra": [ 1, 212, 95, 113, 58, 136, 68, 17, 187, 72, 205, 236, 105, 251, 46, 238, 232, 242, 188, 248, 232, 28, 155, 206, 13, 42, 7, 48, 113, 68, 47, 237, 222, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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