Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c28116cf48bf2c745d472a050f3b261bd86409259950f703789b2ef68d5a18cf

Tx prefix hash: aaec524ea1f00683178e2d0173c4134a3b6e73e2cf0986216bc202cac1828954
Tx public key: 70c20ee5310091698c5b361376b55f74583f6f4ee70fd1c722a3c8cba2e80bd5
Timestamp: 1713464855 Timestamp [UCT]: 2024-04-18 18:27:35 Age [y:d:h:m:s]: 01:057:16:55:00
Block: 1003359 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 302142 RingCT/type: yes/0
Extra: 0170c20ee5310091698c5b361376b55f74583f6f4ee70fd1c722a3c8cba2e80bd502110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7712f3125a28fd99c6dae7077d3b3cb8d6497d6442b6533cbe54bd320a9e8c0a 0.600000000000 1463889 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": 1003369, "vin": [ { "gen": { "height": 1003359 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7712f3125a28fd99c6dae7077d3b3cb8d6497d6442b6533cbe54bd320a9e8c0a" } } ], "extra": [ 1, 112, 194, 14, 229, 49, 0, 145, 105, 140, 91, 54, 19, 118, 181, 95, 116, 88, 63, 111, 78, 231, 15, 209, 199, 34, 163, 200, 203, 162, 232, 11, 213, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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