Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3e1032efb5b8aa3e5f662f52003905baef889cb7e40935f8c5a0a65195b00002

Tx prefix hash: 7ef0e09d63371e536fe7b1526c2495cb31fb3b1c27a9c8dcfb8d043517de905e
Tx public key: b1f9139eac914f4907cddcaa3d7a335a8f2f1ee7bd9c5e4bdfc82a33144f2734
Timestamp: 1756063471 Timestamp [UCT]: 2025-08-24 19:24:31 Age [y:d:h:m:s]: 00:093:20:31:55
Block: 1353617 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67027 RingCT/type: yes/0
Extra: 01b1f9139eac914f4907cddcaa3d7a335a8f2f1ee7bd9c5e4bdfc82a33144f27340211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: febe658f855b6ad3a57c392f57788c1db4457c3fe99c6c798a9ebe942b3872f5 0.600000000000 1841594 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": 1353627, "vin": [ { "gen": { "height": 1353617 } } ], "vout": [ { "amount": 600000000, "target": { "key": "febe658f855b6ad3a57c392f57788c1db4457c3fe99c6c798a9ebe942b3872f5" } } ], "extra": [ 1, 177, 249, 19, 158, 172, 145, 79, 73, 7, 205, 220, 170, 61, 122, 51, 90, 143, 47, 30, 231, 189, 156, 94, 75, 223, 200, 42, 51, 20, 79, 39, 52, 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