Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 52e5488eea12a168ad7a8422bc62b3225e0090cb208b30002db7020cec1e6b80

Tx prefix hash: 443adbc7e5222dd4867f4f61ab2f4668c7733ae0fe776fd0e909f27e59d7de3e
Tx public key: 919af431a15fc0843b3575f6e3b9522b4b8770d8b267c20906c0150781c0aef6
Timestamp: 1750932196 Timestamp [UCT]: 2025-06-26 10:03:16 Age [y:d:h:m:s]: 00:143:06:33:54
Block: 1313103 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100392 RingCT/type: yes/0
Extra: 01919af431a15fc0843b3575f6e3b9522b4b8770d8b267c20906c0150781c0aef602110000000343846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 979c4f52d797e69577d099fc018e1a6da983bcda4e57fbd5315b983aa5f61b9c 0.600000000000 1800740 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": 1313113, "vin": [ { "gen": { "height": 1313103 } } ], "vout": [ { "amount": 600000000, "target": { "key": "979c4f52d797e69577d099fc018e1a6da983bcda4e57fbd5315b983aa5f61b9c" } } ], "extra": [ 1, 145, 154, 244, 49, 161, 95, 192, 132, 59, 53, 117, 246, 227, 185, 82, 43, 75, 135, 112, 216, 178, 103, 194, 9, 6, 192, 21, 7, 129, 192, 174, 246, 2, 17, 0, 0, 0, 3, 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