Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 56beacb2ffa7b32a8f38467cb0c0786f15ccc803383d9e03c4025456e7068e1a

Tx prefix hash: 47e35c6887070fa1cd9a0a93b31ef0117c1d001101430821c796a5d0a53b2ce9
Tx public key: b473f92c8b9fe9e2801cf0393f3283ce928efc3383918e5178bf385d87fe0a41
Timestamp: 1749636889 Timestamp [UCT]: 2025-06-11 10:14:49 Age [y:d:h:m:s]: 00:162:23:20:08
Block: 1302690 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 114166 RingCT/type: yes/0
Extra: 01b473f92c8b9fe9e2801cf0393f3283ce928efc3383918e5178bf385d87fe0a41021100000004bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a2746e0f3e6af67f80a366370c4ec2f6e97499e5c49b5a6371e730f3113084c6 0.600000000000 1790263 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": 1302700, "vin": [ { "gen": { "height": 1302690 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a2746e0f3e6af67f80a366370c4ec2f6e97499e5c49b5a6371e730f3113084c6" } } ], "extra": [ 1, 180, 115, 249, 44, 139, 159, 233, 226, 128, 28, 240, 57, 63, 50, 131, 206, 146, 142, 252, 51, 131, 145, 142, 81, 120, 191, 56, 93, 135, 254, 10, 65, 2, 17, 0, 0, 0, 4, 191, 81, 178, 162, 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