Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a316af1d0caf9e9fc9f621c8d33aa0078e0dc0b63da2e73fd36c96cb4892142

Tx prefix hash: 3ef01a11356cf1a4fb546267bf1b1ab90168443977eaaf1f6b855a0c75280c5b
Tx public key: 2b8ee6d2f3c9cdf556e8f91540e4923c6a60213d2df195f311260b8703ddd35a
Timestamp: 1710257794 Timestamp [UCT]: 2024-03-12 15:36:34 Age [y:d:h:m:s]: 01:241:00:45:28
Block: 976796 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 430968 RingCT/type: yes/0
Extra: 012b8ee6d2f3c9cdf556e8f91540e4923c6a60213d2df195f311260b8703ddd35a0211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cc91af8c19580eef80f13dbc4ab0d17c15ff315b97ceb97804af0910a756a0c4 0.600000000000 1436793 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": 976806, "vin": [ { "gen": { "height": 976796 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cc91af8c19580eef80f13dbc4ab0d17c15ff315b97ceb97804af0910a756a0c4" } } ], "extra": [ 1, 43, 142, 230, 210, 243, 201, 205, 245, 86, 232, 249, 21, 64, 228, 146, 60, 106, 96, 33, 61, 45, 241, 149, 243, 17, 38, 11, 135, 3, 221, 211, 90, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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