Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b08d7d042b3fae936ecaed9386d06216114ae8db946f9fafb8a1bc41314fdebc

Tx prefix hash: 5851ee12159a1c0f2ca10a7cf3f8291fb01b411855a79a6ddbc1ac06f007de79
Tx public key: 2954857ce7c5bca82a4c7bf8f37aa20d8e5e235fc13de7274551a13bd217414f
Timestamp: 1721229420 Timestamp [UCT]: 2024-07-17 15:17:00 Age [y:d:h:m:s]: 00:287:00:31:09
Block: 1067761 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205051 RingCT/type: yes/0
Extra: 012954857ce7c5bca82a4c7bf8f37aa20d8e5e235fc13de7274551a13bd217414f02110000001091e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5f135e5dc885e2704f2099228b5a3c1c3377875c67bf6f584bb433b4597c85e6 0.600000000000 1538664 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": 1067771, "vin": [ { "gen": { "height": 1067761 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5f135e5dc885e2704f2099228b5a3c1c3377875c67bf6f584bb433b4597c85e6" } } ], "extra": [ 1, 41, 84, 133, 124, 231, 197, 188, 168, 42, 76, 123, 248, 243, 122, 162, 13, 142, 94, 35, 95, 193, 61, 231, 39, 69, 81, 161, 59, 210, 23, 65, 79, 2, 17, 0, 0, 0, 16, 145, 225, 60, 4, 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