Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc1c986901bb3f2bbbd149843bfb31deaea1971de90cb05839f023e313333f4e

Tx prefix hash: 7f74e532388e7f55544dc69ca42794eabe82855e1638b33af0e32cbfda3a9e7a
Tx public key: f0f0785d4f427a7f59f63dc9877adb8bbc87f8657fac54ef0b77d6347ade710c
Timestamp: 1730485288 Timestamp [UCT]: 2024-11-01 18:21:28 Age [y:d:h:m:s]: 00:138:05:15:54
Block: 1144395 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98642 RingCT/type: yes/0
Extra: 01f0f0785d4f427a7f59f63dc9877adb8bbc87f8657fac54ef0b77d6347ade710c02110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2d3f3451a08af6bc8cfc431e2901fc613c31246307f378e2cbdacef677f2f00b 0.600000000000 1628604 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": 1144405, "vin": [ { "gen": { "height": 1144395 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2d3f3451a08af6bc8cfc431e2901fc613c31246307f378e2cbdacef677f2f00b" } } ], "extra": [ 1, 240, 240, 120, 93, 79, 66, 122, 127, 89, 246, 61, 201, 135, 122, 219, 139, 188, 135, 248, 101, 127, 172, 84, 239, 11, 119, 214, 52, 122, 222, 113, 12, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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