Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 61c3cba0967eec19423c5ea9e59016caea93ed74498ab7fedad54bc35f17552e

Tx prefix hash: 8ddd1140cc50a70a9eeadb40c4f18f8fd8cd8ab038644aff223a72ef6526c95b
Tx public key: d3a7a5efbd9bb7e3a7d9f83f19e41c438ec2ee986c687499db0bb83abc9088f1
Timestamp: 1745663269 Timestamp [UCT]: 2025-04-26 10:27:49 Age [y:d:h:m:s]: 00:038:19:29:50
Block: 1269809 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 27769 RingCT/type: yes/0
Extra: 01d3a7a5efbd9bb7e3a7d9f83f19e41c438ec2ee986c687499db0bb83abc9088f102110000000b6c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a66458d3425e7195e07b3cd0ae0aa7ce1b13244d9353512325b13022c3ef156 0.600000000000 1757048 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": 1269819, "vin": [ { "gen": { "height": 1269809 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a66458d3425e7195e07b3cd0ae0aa7ce1b13244d9353512325b13022c3ef156" } } ], "extra": [ 1, 211, 167, 165, 239, 189, 155, 183, 227, 167, 217, 248, 63, 25, 228, 28, 67, 142, 194, 238, 152, 108, 104, 116, 153, 219, 11, 184, 58, 188, 144, 136, 241, 2, 17, 0, 0, 0, 11, 108, 152, 170, 61, 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