Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1244796392482bb58af6331f54711bb7d0cbed910c71d3b00a74e083ab6e33f1

Tx prefix hash: 1fb2c36247e70c23d7f124173cfd660f93995bc15d68ac18fb680fcfaeda7e6e
Tx public key: c1cb1df9ea40b677339c19d4894f32399a5e2e34154fb0f2d57786cf5c5a5c23
Timestamp: 1761332561 Timestamp [UCT]: 2025-10-24 19:02:41 Age [y:d:h:m:s]: 00:027:19:39:38
Block: 1397113 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 19900 RingCT/type: yes/0
Extra: 01c1cb1df9ea40b677339c19d4894f32399a5e2e34154fb0f2d57786cf5c5a5c230211000000065dfbbe2a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f41d178a0c163152ec720e70c79a61e21afb890f9869a89145e6e3456f063c91 0.600000000000 1885404 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": 1397123, "vin": [ { "gen": { "height": 1397113 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f41d178a0c163152ec720e70c79a61e21afb890f9869a89145e6e3456f063c91" } } ], "extra": [ 1, 193, 203, 29, 249, 234, 64, 182, 119, 51, 156, 25, 212, 137, 79, 50, 57, 154, 94, 46, 52, 21, 79, 176, 242, 213, 119, 134, 207, 92, 90, 92, 35, 2, 17, 0, 0, 0, 6, 93, 251, 190, 42, 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