Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 46653b3e083e468416e467a1d37fb7b30debfe230779a477bc5e191525244fdf

Tx prefix hash: f1fba3c918166d4b661b63b861b5f173fea1be3bf46217c270eefdef83813ec4
Tx public key: 35e191b24212c8a4e261abf901f7eae3866d9df9e15edfa6dd65e22325657040
Timestamp: 1765957736 Timestamp [UCT]: 2025-12-17 07:48:56 Age [y:d:h:m:s]: 00:046:06:27:36
Block: 1435421 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 32960 RingCT/type: yes/0
Extra: 0135e191b24212c8a4e261abf901f7eae3866d9df9e15edfa6dd65e22325657040021100000001d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0034eb8a559e7a717d6d23ae84847dad22b77651ac5d410d295a393512c4ce42 0.600000000000 1924218 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": 1435431, "vin": [ { "gen": { "height": 1435421 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0034eb8a559e7a717d6d23ae84847dad22b77651ac5d410d295a393512c4ce42" } } ], "extra": [ 1, 53, 225, 145, 178, 66, 18, 200, 164, 226, 97, 171, 249, 1, 247, 234, 227, 134, 109, 157, 249, 225, 94, 223, 166, 221, 101, 226, 35, 37, 101, 112, 64, 2, 17, 0, 0, 0, 1, 214, 225, 157, 124, 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