Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6cfcf133834d29afdf3fb61d3256fef83fc647d7e4aa4b46cc75c67d26933f22

Tx prefix hash: 246b4ba8865dc64a563535f9c43480b9bf42748804c59709fcbec175c4c97a5a
Tx public key: 2ae081da155a1dd58cfe40ea1feffa7811bf8932f50aa34548219978c947909c
Timestamp: 1721897536 Timestamp [UCT]: 2024-07-25 08:52:16 Age [y:d:h:m:s]: 01:159:00:02:17
Block: 1073277 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 372210 RingCT/type: yes/0
Extra: 012ae081da155a1dd58cfe40ea1feffa7811bf8932f50aa34548219978c947909c021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8f6775efd9ba8d5b4c2f8ffd15969fadbf50e8d5ff30e4e0aea088deec3f1ae0 0.600000000000 1545776 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": 1073287, "vin": [ { "gen": { "height": 1073277 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8f6775efd9ba8d5b4c2f8ffd15969fadbf50e8d5ff30e4e0aea088deec3f1ae0" } } ], "extra": [ 1, 42, 224, 129, 218, 21, 90, 29, 213, 140, 254, 64, 234, 31, 239, 250, 120, 17, 191, 137, 50, 245, 10, 163, 69, 72, 33, 153, 120, 201, 71, 144, 156, 2, 17, 0, 0, 0, 9, 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