Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd8070306b6f7e230d2fb6d3924db44ed8646cee442c39d1ba834542d7072bf0

Tx prefix hash: d686e8bef331394438fc6337b70d4b389bd97cb83e2640e879f95d98adf9441c
Tx public key: a3825382cdffd5e191e9a3af15189d9ff6f09fed157ff2fe2fe7103a8cb4ef37
Timestamp: 1733942148 Timestamp [UCT]: 2024-12-11 18:35:48 Age [y:d:h:m:s]: 00:104:07:27:19
Block: 1173059 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74307 RingCT/type: yes/0
Extra: 01a3825382cdffd5e191e9a3af15189d9ff6f09fed157ff2fe2fe7103a8cb4ef370211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aaf4722e35f52eb774e7a791d6c09fb88d81a22332375c9d6ba371d900f6d0fb 0.600000000000 1659036 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": 1173069, "vin": [ { "gen": { "height": 1173059 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aaf4722e35f52eb774e7a791d6c09fb88d81a22332375c9d6ba371d900f6d0fb" } } ], "extra": [ 1, 163, 130, 83, 130, 205, 255, 213, 225, 145, 233, 163, 175, 21, 24, 157, 159, 246, 240, 159, 237, 21, 127, 242, 254, 47, 231, 16, 58, 140, 180, 239, 55, 2, 17, 0, 0, 0, 4, 31, 10, 83, 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