Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 330483e62de2004c11129d40f7cd12268c107626ef3b61d592a83aab4e7fc7b4

Tx prefix hash: d8e9ff920d46d501beaac62f5f6bfea521e869f9200caec165cf2ffb6db5c344
Tx public key: a6c4cacb59cdf529a009cf2d0ffc5d81aed5331d22e09ab76a01fbc0fc1caf25
Timestamp: 1698042063 Timestamp [UCT]: 2023-10-23 06:21:03 Age [y:d:h:m:s]: 01:158:05:09:48
Block: 875719 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 374087 RingCT/type: yes/0
Extra: 01a6c4cacb59cdf529a009cf2d0ffc5d81aed5331d22e09ab76a01fbc0fc1caf2502110000000575e3f0e9000000000000000000

1 output(s) for total of 0.769802724000 dcy

stealth address amount amount idx
00: 1bae3f67673373a96a9ff70dc13ee22de302d2d1bf6b49f5a91c22c2e15c93f1 0.769802724000 1330983 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": 875729, "vin": [ { "gen": { "height": 875719 } } ], "vout": [ { "amount": 769802724, "target": { "key": "1bae3f67673373a96a9ff70dc13ee22de302d2d1bf6b49f5a91c22c2e15c93f1" } } ], "extra": [ 1, 166, 196, 202, 203, 89, 205, 245, 41, 160, 9, 207, 45, 15, 252, 93, 129, 174, 213, 51, 29, 34, 224, 154, 183, 106, 1, 251, 192, 252, 28, 175, 37, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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