Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 11fa2ebe492a9c9c8de08aa0c3b762fbab3313fb958b729d89932034904aef24

Tx prefix hash: a87b4ae1856a22a8963a63620f8a03682ae2b05a7e256832a00253708f1f0606
Tx public key: be3559a240730ae16abe7a3d0d945c2b81da4fa3ebc0edfcc28a5ae4222ef561
Timestamp: 1749173026 Timestamp [UCT]: 2025-06-06 01:23:46 Age [y:d:h:m:s]: 00:166:12:48:48
Block: 1298857 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116714 RingCT/type: yes/0
Extra: 01be3559a240730ae16abe7a3d0d945c2b81da4fa3ebc0edfcc28a5ae4222ef56102110000000a43846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7f827610252c9afefb02ebf851d1cdb40ca7664fe7564b48e18e1c419501b621 0.600000000000 1786388 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": 1298867, "vin": [ { "gen": { "height": 1298857 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7f827610252c9afefb02ebf851d1cdb40ca7664fe7564b48e18e1c419501b621" } } ], "extra": [ 1, 190, 53, 89, 162, 64, 115, 10, 225, 106, 190, 122, 61, 13, 148, 92, 43, 129, 218, 79, 163, 235, 192, 237, 252, 194, 138, 90, 228, 34, 46, 245, 97, 2, 17, 0, 0, 0, 10, 67, 132, 109, 102, 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