Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eecf5f1c08bcda5a404b499bf1196637015f15045fd04f4eab3c04f3d6223c46

Tx prefix hash: bf79d331a6e7bcf93ea16ff4b94d0a97ee8684e7df886e058f63e1215850c182
Tx public key: c4441c8a7168d9b4a59ab4c64c943d640d5d0f34f6e74511487012442d8e35fa
Timestamp: 1724338901 Timestamp [UCT]: 2024-08-22 15:01:41 Age [y:d:h:m:s]: 00:238:15:07:06
Block: 1093540 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170412 RingCT/type: yes/0
Extra: 01c4441c8a7168d9b4a59ab4c64c943d640d5d0f34f6e74511487012442d8e35fa021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 45430037618982b599463acc034a3e57db418f06ec8ba857ac05058cbc462da5 0.600000000000 1568505 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": 1093550, "vin": [ { "gen": { "height": 1093540 } } ], "vout": [ { "amount": 600000000, "target": { "key": "45430037618982b599463acc034a3e57db418f06ec8ba857ac05058cbc462da5" } } ], "extra": [ 1, 196, 68, 28, 138, 113, 104, 217, 180, 165, 154, 180, 198, 76, 148, 61, 100, 13, 93, 15, 52, 246, 231, 69, 17, 72, 112, 18, 68, 45, 142, 53, 250, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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