Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4667adfa913f4c8489af1dd9fbdae2cb1dda104782175f4f9a4a4532bdb60d37

Tx prefix hash: 87878d7beabd9770163906e0e3e89f7c9b401b470906bfd99902907517269b05
Tx public key: 69b2721c3b859c412a165418209cf4c30344ac21f375a21726dceb8c5c8cf266
Timestamp: 1744476495 Timestamp [UCT]: 2025-04-12 16:48:15 Age [y:d:h:m:s]: 00:265:15:05:52
Block: 1259974 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187641 RingCT/type: yes/0
Extra: 0169b2721c3b859c412a165418209cf4c30344ac21f375a21726dceb8c5c8cf266021100000007dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6bfda57a6c63a810eade8d0c3f22babe38f14c4f997e4f11c74adfb4dbb8aa7f 0.600000000000 1747125 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": 1259984, "vin": [ { "gen": { "height": 1259974 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6bfda57a6c63a810eade8d0c3f22babe38f14c4f997e4f11c74adfb4dbb8aa7f" } } ], "extra": [ 1, 105, 178, 114, 28, 59, 133, 156, 65, 42, 22, 84, 24, 32, 156, 244, 195, 3, 68, 172, 33, 243, 117, 162, 23, 38, 220, 235, 140, 92, 140, 242, 102, 2, 17, 0, 0, 0, 7, 219, 181, 113, 193, 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