Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 81a34bad311058a3a3c7e09353e1e181f133172279d5d01e94a6cd9581f65be3

Tx prefix hash: ddf57c049e476852f9bd392795ba2fcd8c9845edc930926cb9c0ef682f272b00
Tx public key: 8f5a8c9a6c5e800937d0b33e9821a37722c95800bc7db1d3252155a156146f6a
Timestamp: 1706323972 Timestamp [UCT]: 2024-01-27 02:52:52 Age [y:d:h:m:s]: 01:103:01:37:40
Block: 944147 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 334765 RingCT/type: yes/0
Extra: 018f5a8c9a6c5e800937d0b33e9821a37722c95800bc7db1d3252155a156146f6a02110000000a59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f64173d62afdc1d7e6aad16040a74edc59fdd6547ff603436cb9feeb52a7b60c 0.600000000000 1402377 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": 944157, "vin": [ { "gen": { "height": 944147 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f64173d62afdc1d7e6aad16040a74edc59fdd6547ff603436cb9feeb52a7b60c" } } ], "extra": [ 1, 143, 90, 140, 154, 108, 94, 128, 9, 55, 208, 179, 62, 152, 33, 163, 119, 34, 201, 88, 0, 188, 125, 177, 211, 37, 33, 85, 161, 86, 20, 111, 106, 2, 17, 0, 0, 0, 10, 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