Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a8bcf0ff1ba999a8a10c96bf72b4f3f77730a1af5b56c27fd3fe1eb450e5fd76

Tx prefix hash: 267c6f735bf475ff9d7cb6c915466d046086b499e739d7eca332f9c620917208
Tx public key: 3e6ef2e2e71ad865ef14cc8be57280955bf5cbb6bdd9ff270b12aea2eba88371
Timestamp: 1617068210 Timestamp [UCT]: 2021-03-30 01:36:50 Age [y:d:h:m:s]: 04:043:03:04:20
Block: 229377 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1050974 RingCT/type: yes/0
Extra: 013e6ef2e2e71ad865ef14cc8be57280955bf5cbb6bdd9ff270b12aea2eba8837102110000000cece3035d000000000000000000

1 output(s) for total of 106.654543844000 dcy

stealth address amount amount idx
00: 8b3ed426833a3fc12aebecbcf034cd75c337a804354a04ed6a490b57f14f059a 106.654543844000 475917 of 0

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": 229387, "vin": [ { "gen": { "height": 229377 } } ], "vout": [ { "amount": 106654543844, "target": { "key": "8b3ed426833a3fc12aebecbcf034cd75c337a804354a04ed6a490b57f14f059a" } } ], "extra": [ 1, 62, 110, 242, 226, 231, 26, 216, 101, 239, 20, 204, 139, 229, 114, 128, 149, 91, 245, 203, 182, 189, 217, 255, 39, 11, 18, 174, 162, 235, 168, 131, 113, 2, 17, 0, 0, 0, 12, 236, 227, 3, 93, 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