Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b58d085bafcc8ba42a59fe6874677ef6ecc25d412e30b0a09586af66e07e222

Tx prefix hash: d765d1a84742165235d431278b4cbfa9cb083755b4e3c3147d4be07a6829a0a6
Tx public key: 064997e99521c501ceae6101c6940e346c6e69bcc9de2de8a7d4515237fcbd26
Timestamp: 1742078965 Timestamp [UCT]: 2025-03-15 22:49:25 Age [y:d:h:m:s]: 00:298:13:54:20
Block: 1240155 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 211184 RingCT/type: yes/0
Extra: 01064997e99521c501ceae6101c6940e346c6e69bcc9de2de8a7d4515237fcbd2602110000000f1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 303db2cb9fac0ffbf841fa1f6d1c5e9631f4d80e679d2f03403da63f744b6775 0.600000000000 1727120 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": 1240165, "vin": [ { "gen": { "height": 1240155 } } ], "vout": [ { "amount": 600000000, "target": { "key": "303db2cb9fac0ffbf841fa1f6d1c5e9631f4d80e679d2f03403da63f744b6775" } } ], "extra": [ 1, 6, 73, 151, 233, 149, 33, 197, 1, 206, 174, 97, 1, 198, 148, 14, 52, 108, 110, 105, 188, 201, 222, 45, 232, 167, 212, 81, 82, 55, 252, 189, 38, 2, 17, 0, 0, 0, 15, 31, 10, 83, 235, 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