Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4c50b077ee4bf8ce61f154ddd64dbc3bbbb3040167b048ab7f311ff06082b65

Tx prefix hash: 414aa640f3a38f68156ad0bb14e6a1a154e82eac6ed5d2c4b6435f42f5163ef4
Tx public key: 5aa6dce442a795c4070d24a24c1c10c6dbd4a25174005626061e3173d17f5877
Timestamp: 1761833704 Timestamp [UCT]: 2025-10-30 14:15:04 Age [y:d:h:m:s]: 00:008:19:19:44
Block: 1401262 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 6298 RingCT/type: yes/0
Extra: 015aa6dce442a795c4070d24a24c1c10c6dbd4a25174005626061e3173d17f587702110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2b37fa6ca0c4b70e7cbc6cf24c1df157f6fb34c533c8f78bf117d1bc79a1035c 0.600000000000 1889581 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": 1401272, "vin": [ { "gen": { "height": 1401262 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2b37fa6ca0c4b70e7cbc6cf24c1df157f6fb34c533c8f78bf117d1bc79a1035c" } } ], "extra": [ 1, 90, 166, 220, 228, 66, 167, 149, 196, 7, 13, 36, 162, 76, 28, 16, 198, 219, 212, 162, 81, 116, 0, 86, 38, 6, 30, 49, 115, 209, 127, 88, 119, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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