Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 561a19f64c522c51a47689e496c578d08399dd096edc604c3c0e0d3ff987ac21

Tx prefix hash: bd447953f4a4638dcbc5b784a753ee0c4c6ebc271927ddd471d6905e09db8232
Tx public key: c981e7618a5d4eb96c231e58d6c0ae3e4fd41ac16ebc140685cafdf17fd3f7b5
Timestamp: 1723239214 Timestamp [UCT]: 2024-08-09 21:33:34 Age [y:d:h:m:s]: 00:280:10:20:45
Block: 1084404 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200344 RingCT/type: yes/0
Extra: 01c981e7618a5d4eb96c231e58d6c0ae3e4fd41ac16ebc140685cafdf17fd3f7b5021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bc1fe827211e497b9cef2fc411608cd7f14b01a307e0567d14a89c83cf68b0a5 0.600000000000 1558673 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": 1084414, "vin": [ { "gen": { "height": 1084404 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc1fe827211e497b9cef2fc411608cd7f14b01a307e0567d14a89c83cf68b0a5" } } ], "extra": [ 1, 201, 129, 231, 97, 138, 93, 78, 185, 108, 35, 30, 88, 214, 192, 174, 62, 79, 212, 26, 193, 110, 188, 20, 6, 133, 202, 253, 241, 127, 211, 247, 181, 2, 17, 0, 0, 0, 7, 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