Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b0616ffcd0376c90ade475c165414244c8aea53861cbb558f74afa8823bf0f3b

Tx prefix hash: 0a43665ed3f57fd6c651861ea0ff1322d9f65b3f2b9bc68bc690d5094fcf6a7b
Tx public key: ac212eb342a072c508a9afc28925b7bf45dab5802539ccd17e282e40b88a5bc9
Timestamp: 1703682235 Timestamp [UCT]: 2023-12-27 13:03:55 Age [y:d:h:m:s]: 01:085:22:38:27
Block: 922278 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 322531 RingCT/type: yes/0
Extra: 01ac212eb342a072c508a9afc28925b7bf45dab5802539ccd17e282e40b88a5bc902110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b758d2959f8d0e730c5df140a6bf91a96a50ca6022b0eafc6d83b1ef379ae8d4 0.600000000000 1379974 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": 922288, "vin": [ { "gen": { "height": 922278 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b758d2959f8d0e730c5df140a6bf91a96a50ca6022b0eafc6d83b1ef379ae8d4" } } ], "extra": [ 1, 172, 33, 46, 179, 66, 160, 114, 197, 8, 169, 175, 194, 137, 37, 183, 191, 69, 218, 181, 128, 37, 57, 204, 209, 126, 40, 46, 64, 184, 138, 91, 201, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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