Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 40f17043c9521f1497d577cbf67bbaf3daff0f627333a24b7252bb4da32c88cf

Tx prefix hash: 081b5d586bb07ae08c770c8990427bfc085fad9d98c5d5fe5db1ebcfe1a20b7d
Tx public key: 72f306d0b02ad69ad4df43717b31b0b4f07fc56bf022cf8e40f4c03f56aaed31
Timestamp: 1724856321 Timestamp [UCT]: 2024-08-28 14:45:21 Age [y:d:h:m:s]: 00:213:19:45:13
Block: 1097814 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 152670 RingCT/type: yes/0
Extra: 0172f306d0b02ad69ad4df43717b31b0b4f07fc56bf022cf8e40f4c03f56aaed31021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e687e33fc95b162a96fd3094fce1148127c4e12764d0e701b627480a21bf26bf 0.600000000000 1573313 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": 1097824, "vin": [ { "gen": { "height": 1097814 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e687e33fc95b162a96fd3094fce1148127c4e12764d0e701b627480a21bf26bf" } } ], "extra": [ 1, 114, 243, 6, 208, 176, 42, 214, 154, 212, 223, 67, 113, 123, 49, 176, 180, 240, 127, 197, 107, 240, 34, 207, 142, 64, 244, 192, 63, 86, 170, 237, 49, 2, 17, 0, 0, 0, 6, 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