Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 33292828a7e80645684c95e33e21d738dd4be9c865e69b1c17b83f8c47cdcde6

Tx prefix hash: e2a5b7c63ba34e9a6ada66fc854ff67d1288aa0ca688964fdaca22b78e7f4f78
Tx public key: 652a0544654c7e1abb2c219068b5d001e1c4dd7b2b8863bc79ac46ef04cdb5c3
Timestamp: 1726567506 Timestamp [UCT]: 2024-09-17 10:05:06 Age [y:d:h:m:s]: 00:194:01:27:32
Block: 1111999 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 138511 RingCT/type: yes/0
Extra: 01652a0544654c7e1abb2c219068b5d001e1c4dd7b2b8863bc79ac46ef04cdb5c3021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d39cc53070a9e18f531c7aaf959857015f9314886702a5995382dfaf51d6d4a1 0.600000000000 1591160 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": 1112009, "vin": [ { "gen": { "height": 1111999 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d39cc53070a9e18f531c7aaf959857015f9314886702a5995382dfaf51d6d4a1" } } ], "extra": [ 1, 101, 42, 5, 68, 101, 76, 126, 26, 187, 44, 33, 144, 104, 181, 208, 1, 225, 196, 221, 123, 43, 136, 99, 188, 121, 172, 70, 239, 4, 205, 181, 195, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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