Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 641efe4bb4c2e72865124ff2974645d7cf6b9a089dd0ed57e4aa1ba254f720fc

Tx prefix hash: 66acb50b1188925a588cd1ac1332eddca9f9281a80830069ca9b160b55fa1423
Tx public key: a3e7f5949f4dc751508890269ff2a8fbce6359405816a47d2b8ab771181c1b4e
Timestamp: 1754709515 Timestamp [UCT]: 2025-08-09 03:18:35 Age [y:d:h:m:s]: 00:172:09:05:36
Block: 1343229 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 122235 RingCT/type: yes/0
Extra: 01a3e7f5949f4dc751508890269ff2a8fbce6359405816a47d2b8ab771181c1b4e0211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c7be7bc62844617f84e3ff7006351f0efa0b2ffdc6bf2e14308c6e1be7ff5dad 0.600000000000 1831068 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": 1343239, "vin": [ { "gen": { "height": 1343229 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c7be7bc62844617f84e3ff7006351f0efa0b2ffdc6bf2e14308c6e1be7ff5dad" } } ], "extra": [ 1, 163, 231, 245, 148, 159, 77, 199, 81, 80, 136, 144, 38, 159, 242, 168, 251, 206, 99, 89, 64, 88, 22, 164, 125, 43, 138, 183, 113, 24, 28, 27, 78, 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