Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eb9b56b4a75a97b1f7f0b8d9465ac917382f152fa9417037e2b10f4df00a8442

Tx prefix hash: eca7ffb0e4800cdf9a4b98d37576ab49cee35f552f9cb635320d3bd5a05b4190
Tx public key: b68ea98d3dbfe050da0ebbce683d51f80c07b22332747e2070fcd58051f3ffd5
Timestamp: 1726753804 Timestamp [UCT]: 2024-09-19 13:50:04 Age [y:d:h:m:s]: 00:112:15:02:49
Block: 1113547 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80533 RingCT/type: yes/0
Extra: 01b68ea98d3dbfe050da0ebbce683d51f80c07b22332747e2070fcd58051f3ffd5021100000001e914dd15000000000000000000

1 output(s) for total of 0.607980000000 dcy

stealth address amount amount idx
00: cf4c59088247a0a60c717c4faa7daa6557ec2f86706478f99896c17e5b281f1d 0.607980000000 1593254 of 0

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": 1113557, "vin": [ { "gen": { "height": 1113547 } } ], "vout": [ { "amount": 607980000, "target": { "key": "cf4c59088247a0a60c717c4faa7daa6557ec2f86706478f99896c17e5b281f1d" } } ], "extra": [ 1, 182, 142, 169, 141, 61, 191, 224, 80, 218, 14, 187, 206, 104, 61, 81, 248, 12, 7, 178, 35, 50, 116, 126, 32, 112, 252, 213, 128, 81, 243, 255, 213, 2, 17, 0, 0, 0, 1, 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