Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4a12abe694c0d41c8ba0fe72b20e173e8b769ba0a692c36bf09c6f9a3a2abb5

Tx prefix hash: 6c20846512ad9432bf0f60408e54d5ccc119569e8869d1c6dc883651d3e0cc30
Tx public key: ca99f3a2ccc3dbf83b8ffbfce08e7101f6c4e4e294a515afc1166432156a3f5d
Timestamp: 1722715011 Timestamp [UCT]: 2024-08-03 19:56:51 Age [y:d:h:m:s]: 00:244:01:06:33
Block: 1080058 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 174319 RingCT/type: yes/0
Extra: 01ca99f3a2ccc3dbf83b8ffbfce08e7101f6c4e4e294a515afc1166432156a3f5d021100000012e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b7d08a6e751ffe284a6b8916c0eabfcd577ff188ba3c8c663012d8879e8bbf08 0.600000000000 1553271 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": 1080068, "vin": [ { "gen": { "height": 1080058 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b7d08a6e751ffe284a6b8916c0eabfcd577ff188ba3c8c663012d8879e8bbf08" } } ], "extra": [ 1, 202, 153, 243, 162, 204, 195, 219, 248, 59, 143, 251, 252, 224, 142, 113, 1, 246, 196, 228, 226, 148, 165, 21, 175, 193, 22, 100, 50, 21, 106, 63, 93, 2, 17, 0, 0, 0, 18, 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