Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1bbe4ee99b08dade9a563658f183eab1f025d5aea58f4253765394f1d8815aee

Tx prefix hash: aa41f500d65148b2f32c1e813e9f5b13619dece61c9e936ed4c68baf587cc9d0
Tx public key: c46a83e5d08496321627a7aea08a55fa11987f63a78f0bd8edc3b2f58efb6f69
Timestamp: 1756157453 Timestamp [UCT]: 2025-08-25 21:30:53 Age [y:d:h:m:s]: 00:134:17:28:00
Block: 1354390 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 96301 RingCT/type: yes/0
Extra: 01c46a83e5d08496321627a7aea08a55fa11987f63a78f0bd8edc3b2f58efb6f690211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 64aabf23bb834df2ebc0a573897a82f6e7afe0eefb6171ecfe8015f8d961fc1b 0.600000000000 1842377 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": 1354400, "vin": [ { "gen": { "height": 1354390 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64aabf23bb834df2ebc0a573897a82f6e7afe0eefb6171ecfe8015f8d961fc1b" } } ], "extra": [ 1, 196, 106, 131, 229, 208, 132, 150, 50, 22, 39, 167, 174, 160, 138, 85, 250, 17, 152, 127, 99, 167, 143, 11, 216, 237, 195, 178, 245, 142, 251, 111, 105, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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