Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e952f7684249264d9ae48297fc961e33eefc92140d1b8054fbfb0db70db33f38

Tx prefix hash: 0c3c58ca5b5130853800405b064a28d6a171c708df21a7e62d82ea33d974aef8
Tx public key: f7c8f6fe1ce5fb92f2b00401ec72b0e7f39432378f4b21efe38d7ff51808797e
Timestamp: 1754852434 Timestamp [UCT]: 2025-08-10 19:00:34 Age [y:d:h:m:s]: 00:058:01:57:19
Block: 1344322 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 40655 RingCT/type: yes/0
Extra: 01f7c8f6fe1ce5fb92f2b00401ec72b0e7f39432378f4b21efe38d7ff51808797e0211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 256da41eb0607917c16e58030647e99e65935763467f1a2f63c52c0eac694bbf 0.600000000000 1832205 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": 1344332, "vin": [ { "gen": { "height": 1344322 } } ], "vout": [ { "amount": 600000000, "target": { "key": "256da41eb0607917c16e58030647e99e65935763467f1a2f63c52c0eac694bbf" } } ], "extra": [ 1, 247, 200, 246, 254, 28, 229, 251, 146, 242, 176, 4, 1, 236, 114, 176, 231, 243, 148, 50, 55, 143, 75, 33, 239, 227, 141, 127, 245, 24, 8, 121, 126, 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